feat(dashboard): account burn rate card with settings toggle#218
feat(dashboard): account burn rate card with settings toggle#218mws-weekend-projects wants to merge 1 commit intoSoju06:mainfrom
Conversation
- add Account burn rate chart/stat between Cost and Error rate - add Appearance setting to toggle chart visibility (default on) - improve burn calculation fallback/projection and quota_exceeded handling - include legacy settings schema compatibility defaults
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: acb9aa6fdc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if (windowKey === "secondary") { | ||
| if (isFiniteNumber(fallbackProjectedEquivalent)) { | ||
| return clampBurnEquivalent( | ||
| burnEquivalent === null ? fallbackProjectedEquivalent : Math.max(burnEquivalent, fallbackProjectedEquivalent), | ||
| maxEquivalent, |
There was a problem hiding this comment.
The primary burn-rate path never applies the projection fallback that you added for secondary, so it can materially under-report burn whenever the 5h window is already partially consumed. In plusAccountsBurnEquivalent, burnEquivalent is derived from remainingCredits * burnRate / capacity (future burn only), and the max(..., fallbackProjectedEquivalent) correction is gated to windowKey === "secondary"; e.g., at 50% used with burnRate=1, the card shows 0.5 for primary even though projected full-window consumption is 1.0. This affects dashboards with active primary depletion data and can mislead operators about current burn pace.
Useful? React with 👍 / 👎.
2 participants
The burn rate shows how fast your Plus accounts are currently being consumed:
Example: Primary 0.5 · Secondary 1.7 means:
you’re currently consuming about 0.5 accounts in the 5-hour window
and about 1.7 accounts over 7 days (projected from current pace).
add Account burn rate chart/stat between Cost and Error rate
add Appearance setting to toggle chart visibility (default on)